Details

In our build artifacts for engine-dom and engine-server, I would like to be able to replace runtime flags with true and false for tree-shaking purposes. (I.e. a consumer can tree-shake out any runtime features they are not using.)

This is possible today with e.g. @rollup/plugin-replace, but currently our build artifacts contain things like:

if (runtimeFlags.ENABLE_REACTIVE_SETTER) {

... which would require:

replace({
  'runtimeFlags.ENABLE_REACTIVE_SETTER': 'false',
  preventAssignment: true
})

I propose renaming runtimeFlags to the more explicit lwcRuntimeFlags, because:

1. It makes it more obvious that you're replacing an LWC runtime flag.
2. It matches the name of the global anyway.
3. It completely eliminates the possibility of collision with some other library/framework using a variable called runtimeFlags.

So we would have:

if (lwcRuntimeFlags.ENABLE_REACTIVE_SETTER) {

and:

replace({
  'lwcRuntimeFlags.ENABLE_REACTIVE_SETTER': 'false',
  preventAssignment: true
})

Does this pull request introduce a breaking change?

• ✅ No, it does not introduce a breaking change.

Does this pull request introduce an observable change?

• ✅ No, it does not introduce an observable change.

GUS work item